-
-
Notifications
You must be signed in to change notification settings - Fork 224
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
BUGFIX: Partial publish breaks uri and change Projection #5293
Conversation
WIP DO NOT MERGE, it's just a test showing the behavior. |
The latest commit fixes the issue at least for new events, but we still need a solution for existing events. |
The fix is more of a proof-of-concept. I will work on virtual workspaces now and adjust the fix to that once it's done. |
Fyi this was my virtual workspace name draft: #5167 |
also this can then be fixed with catchup hooks neos-development-collection/Neos.Neos/Classes/AssetUsage/CatchUpHook/AssetUsageCatchUpHook.php Lines 51 to 60 in b11026d
|
A partial publish results in events annotated for "live" workspace yet are not in the "live" content stream. This is due to a fork of the live content stream being created with the partially published events in, which is then published to the actual live content stream. This leaves behind duplicate events both containing "workspaceName: live" yet only one of them is in the live content stream. A catchup or replay will fail however due to duplicate database entries for the reflections relying on anything with "workspaceName: live" being actually in the live content stream. The provided test fails showing the behavior.
ef2d459
to
3dd9069
Compare
I have no clue why these Behat tests are failing, they are fine on my machine and I can't see the relation between the test and what I changed in this. |
i cherry picked the test to our big pr and also documented why we are not going that way in #5327 so that why we can close this |
A partial publish results in events annotated for "live" workspace yet are not in the "live" content stream.
This is due to a fork of the live content stream being created with the partially published events in, which is then published to the actual live content stream.
This leaves behind duplicate events both containing "workspaceName: live" yet only one of them is in the live content stream. A catchup or replay will fail however due to duplicate database entries for the projections relying on anything with "workspaceName: live" being actually in the live content stream.
The provided test fails showing the behavior.
Upgrade instructions
Review instructions
Checklist
FEATURE|TASK|BUGFIX
!!!
and have upgrade-instructions